Index
Subject
: [lug] Digest (5 messages)
From
: lug-owner@lists.ncsu.[redacted]
Date
: Wed, 30 Sep 2015 13:23:17 -0400
The Lug Digest
Volume 1 : Issue 355 : "text" Format
Messages in this Issue:
201509/28 : NCSU LUG meeting tomorrow, 9/29, 7pm EB2
Ian Kilgore <imkilgor@ncsu.[redacted]>
201509/30 : Re: NCSU LUG meeting tomorrow, 9/29, 7pm EB2
Quentin Young <qlyoung@ncsu.[redacted]>
201509/29 : Re: Automating Metaflac
Alex Jones <starfoxx139@gmail.[redacted]>
201509/31 : Re: Making Clickable web elements Keyboard Accessible.
Vaclav Petras <vpetras@ncsu.[redacted]>
201509/32 : Re: Making Clickable web elements Keyboard Accessible.
Chris Webster <chris.webster@ncsu.[redacted]>
----------------------------------------------------------------------
Date: Mon, 28 Sep 2015 09:26:55 -0400
From: Ian Kilgore <imkilgor@ncsu.[redacted]>
To: "lug@lists.ncsu.[redacted]" <lug@lists.ncsu.[redacted]>
Subject: NCSU LUG meeting tomorrow, 9/29, 7pm EB2
Message-ID: <CAOyKK9t7r-0a=7qTNEpxrXAZe=2Hpc5s7d-iVdhgz8r8PU6Bnw@mail.gmail.[redacted]>
Hi friends,
Tomorrow Quentin Young (albatron) will give a talk about linux desktop
environments, covering everything from the commandline to a full desktop
environment, including X11, window managers, launchers, tools, etc.
Room is TBD so we'll meet in the lobby of EB2 around 7pm (east wing, CS
side) and go from there. We'll put up some signs for any latecomers.
Dinner to follow!
Thanks,
Ian
[Attachment of type text/html removed.]
------------------------------
Date: Tue, 29 Sep 2015 19:05:38 -0400
From: Quentin Young <qlyoung@ncsu.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Re: NCSU LUG meeting tomorrow, 9/29, 7pm EB2
Message-ID: <CANhSzx3+ei5GC8Vkwe2WBR8gSvznwsRZz9654oDYkcsRhVHBnQ@mail.gmail.[redacted]>
Update: we are meeting in EB2 Room 1212 tonight.
On Sep 28, 2015 9:27 AM, "Ian Kilgore" <imkilgor@ncsu.[redacted]> wrote:
> Hi friends,
>
> Tomorrow Quentin Young (albatron) will give a talk about linux desktop
> environments, covering everything from the commandline to a full desktop
> environment, including X11, window managers, launchers, tools, etc.
>
> Room is TBD so we'll meet in the lobby of EB2 around 7pm (east wing, CS
> side) and go from there. We'll put up some signs for any latecomers.
>
> Dinner to follow!
>
> Thanks,
> Ian
>
[Attachment of type text/html removed.]
------------------------------
Date: Tue, 29 Sep 2015 00:13:43 +0000
From: Alex Jones <starfoxx139@gmail.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Re: Automating Metaflac
Message-ID: <CAD+uwrq83bOYExPu5rF_teR4moYyDrGiQpWxsbtH8q_hJY64KQ@mail.gmail.[redacted]>
This sounds super interesting, If you want to try to hammer out a script
for you can I get a $(pwd) and $(ls) a folder finished and unfinished?
If not, here are my thoughts:
filelist.sh will replace numbers from the middle of a file name too, so
it'll mess up song titles like 22000 Days
<https://www.youtube.com/watch?v=gbLCP9ENemI> replacing the sed chain with
something else, maybe regex, or a smarter scanner might be more effective,
maybe this isn't a problem with your song titles though.
PS: recursive scan of the directory can be done with a basic bash for loop:
$ROOT=$(pwd) for f in $(find . -name '*_*'); do cd $(dirname $f); mv
$(basename $f) $(sed s/_/ /g) "$(basename $f)"; cd $ROOT; done
I took the basic loop from here, and added some basic cd commands to ensure
that the relative paths returned by find could be used to navigate, so that
we could just basename the file.
http://stackoverflow.com/questions/4638874/how-to-loop-through-a-directory-recursively
On Sun, Sep 27, 2015 at 1:28 PM Jeffery Mewtamer <mewtamer@gmail.[redacted]> wrote:
> Recently, I've started amassing a Library of Audiobooks in Audio CD
> format and ripping them to flac with abcde as I've been doing with
> music CDs for years. However, I've run into a few snags from an
> organizational standpoint.
>
> Ideally, I want one chapter per file with each file having the
> following path anf filename:
> ~/Library/Author Name/Book Title/## Chapter Title.flac
> With each file having the following tags:
> Artist=Author Name
> Album=Book Title
> Title= Chapter Title
> Track= Chapter Number
>
> Sox provides an elegant solution for Books-on-CD that have multiple
> tracks per chapter, and the only real issue I'm having with file names
> is that abcde uses underscores in filenames and I prefer spaces, at
> least when a disc has a CDDB hit and I only have to change track
> number to chapter number.
>
> Where I'm having problems is with tags. I've figured out enough about
> metaflac to make a script to tag an entire book worth of files as well
> as a second script to generate a list of Chapter Titles and file names
> to plug into the metaflac script(it does rely on the files already
> being appropriately named), but there's still a lot of cutting and
> pasting for each book I tag in this way.
>
> Any suggestions on how I could further automate the process? In
> addition to the script with spaces for file names and chapter
> titles(tag.sh) and the script that I made for generating a list of
> chapter titles and file names(file_list.sh) I've included the complete
> scripts for the two books I've already tagged in this way.
>
> Also, if anyone know of any command line tools that could assist in
> any of the following it would be appreciated:
> Recursively scanning a dirctory and replacing all _ in filenames with
> spaces.
> Assisting with transliterating non-latin(primarily Japanese) filenames
> to a Latin character set.
> Transliterating non-Latin tags in flac files to a latin character
> set(again, primarily dealing with Japanese-to-Latin Alphabet)..
>
[Attachment of type text/html removed.]
------------------------------
Date: Wed, 30 Sep 2015 13:05:02 -0400
From: Vaclav Petras <vpetras@ncsu.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Re: Making Clickable web elements Keyboard Accessible.
Message-ID: <CAJeX9NryExL42ji=sLG+P3Rtpj7TLY9E4o1xefSMHa6=3Sxq-A@mail.gmail.[redacted]>
Hi Jeffery and Quentin,
I don't have any solution but since I spent some time understanding the
issue, let me share where I got.
When using Tab key in both Firefox and Chromium the Register button gets
skipped. The difference between this button and other button is that
instead of href attribute it has onclick. Apparently JavaScript is used to
submit the form after validation. Anyway, I don't see a reason why the
browser is skipping a element without href. Adding an empty href results in
Tab key working but click has the unfortunate consequence that it follows
it, i.e. page gets reloaded.
Perhaps the issue is that the page is using element a where input or button
elements would be more appropriate.
I ran the page through W3C validator and and WAVE accessibility check but
both are silent.
Vashek
On Tue, Sep 22, 2015 at 3:02 PM, Quentin Young <qlyoung@ncsu.[redacted]> wrote:
> I was looking through the Orca documentation last night and it appears
> that using 'a' to select clickable elements is functionality provided by
> Orca. If 'a' puts focus on the clickable element, you should be able to
> activate the element with the enter key, correct? Am I misunderstanding?
>
> If that doesn't work, I have a different solution, although it is
> something of a hack. On the page you linked, by inserting a tab index
> attribute on the register button element using the browser's html editor,
> the browser will allow you to tab onto the button as you normally would.
>
> It would probably be pretty easy to write a grease monkey script, or
> something similar, that simply adds a tab index to each element on the
> page, to make sure that all elements can be tabbed to. If you're interested
> in that I would be happy to play with the idea and see what I can come up
> with.
>
> Quentin
>
> On Tue, Sep 22, 2015 at 4:33 AM, Jeffery Mewtamer <mewtamer@gmail.[redacted]>
> wrote:
>
>> Sorry for not thinking to include an example of a page showing the
>> problem.
>>
>> Here's the page that pushed me from finding it an easily ignored
>> inconvenience to wanting to find a solution:
>> https://www.zintellect.com/Account/Register
>>
>> On the linked page, the offending element is the register link(tabbing
>> jumps straight from cancel to help).
>>
>> Okay, just thought to do an experiment: I don't know if the function
>> is part of Iceweasel/Firefox or an accessibility feature added by
>> Orca, but pressing various buttons on my keyboard will cause my cursor
>> to jump between page elements of a given type. Normally, I just use
>> h(for headings at all levels) 1-6(for headings at specific levels) and
>> t(for tables) for quickly navigating pages, but it turns out that
>> there is such a shortcut for clickables(the a key). This should mean I
>> now have a way of putting focus on a clickable and just need a way to
>> activate them without a mouse(though clicking my laptop's touchpad
>> might work if I reinstall xserver-input-mouse, but then I have to
>> worry about the noise generated when accidental contact is made with
>> the touchpad).
>>
>> On 9/22/15, Quentin Young <qlyoung@ncsu.[redacted]> wrote:
>> > Hi Jeffery,
>> >
>> > Can you possibly link me to a webpage exhibiting this behavior? I
>> haven't
>> > found anything existing that fits your needs but I have an idea for an
>> easy
>> > implementation.
>> >
>> > Quentin
>> >
>> > On Mon, Sep 21, 2015 at 6:37 AM, Jeffery Mewtamer <mewtamer@gmail.[redacted]>
>> > wrote:
>> >
>> >> Good morning,
>> >>
>> >> I use Iceweasel/Firefox in combination with the Orca screenreader for
>> >> browsing the Internet, and there's one bit of bad web design that
>> >> keeps rearing its ugly head: Buttons and other web controls that orca
>> >> identifies as being clickable. I can't use a mouse, they get skipped
>> >> over when tabbing between links and form elements, and the enter and
>> >> space keys do nothing if I manually position the cursor on them.
>> >> Google would indicate that this is a fairly well known problem in the
>> >> area of web accessibility, but every fix I've found via Google has
>> >> been targeted at web designers who want the greater visual flexibility
>> >> such elements allow without rendering their pages unusable to screen
>> >> reader users. I've been unable to find anything that assists with
>> >> making these elements accessible on the end-user side of things.
>> >>
>> >> Anyone have any suggestions for possible solutions?incerely,
>> >>
>> >> Jeffery Wright
>> >> President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
>> >> Former Secretary, Student Government Association, College of the
>> >> Albemarle.
>> >>
>> >
>> >
>> >
>> > --
>> > Quentin Young
>> > Vice President, LUG @ NC State
>> >
>>
>>
>> --
>> Sincerely,
>>
>> Jeffery Wright
>> President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
>> Former Secretary, Student Government Association, College of the
>> Albemarle.
>>
>
>
>
> --
> Quentin Young
> Vice President, LUG @ NC State
>
[Attachment of type text/html removed.]
------------------------------
Date: Wed, 30 Sep 2015 13:22:53 -0400
From: Chris Webster <chris.webster@ncsu.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Re: Making Clickable web elements Keyboard Accessible.
Message-ID: <CAL_ebDkV-6bji4XKSc90VieVhCzH8Lzj3dshntSSbZss-qz23w@mail.gmail.[redacted]>
If you add href="#" to the button attributes (instead of an empty href),
the onclick is activated without reloading the page. Not sure what
collateral consequences that has for assistive technologies, if any.
Cheers,
Chris
--
Chris Webster
ServiceNow Business Analyst
Office of Information Technology
North Carolina State University
On Wed, Sep 30, 2015 at 1:05 PM, Vaclav Petras <vpetras@ncsu.[redacted]> wrote:
> Hi Jeffery and Quentin,
>
> I don't have any solution but since I spent some time understanding the
> issue, let me share where I got.
>
> When using Tab key in both Firefox and Chromium the Register button gets
> skipped. The difference between this button and other button is that
> instead of href attribute it has onclick. Apparently JavaScript is used to
> submit the form after validation. Anyway, I don't see a reason why the
> browser is skipping a element without href. Adding an empty href results in
> Tab key working but click has the unfortunate consequence that it follows
> it, i.e. page gets reloaded.
>
> Perhaps the issue is that the page is using element a where input or
> button elements would be more appropriate.
>
> I ran the page through W3C validator and and WAVE accessibility check but
> both are silent.
>
> Vashek
>
> On Tue, Sep 22, 2015 at 3:02 PM, Quentin Young <qlyoung@ncsu.[redacted]> wrote:
>
>> I was looking through the Orca documentation last night and it appears
>> that using 'a' to select clickable elements is functionality provided by
>> Orca. If 'a' puts focus on the clickable element, you should be able to
>> activate the element with the enter key, correct? Am I misunderstanding?
>>
>> If that doesn't work, I have a different solution, although it is
>> something of a hack. On the page you linked, by inserting a tab index
>> attribute on the register button element using the browser's html editor,
>> the browser will allow you to tab onto the button as you normally would.
>>
>> It would probably be pretty easy to write a grease monkey script, or
>> something similar, that simply adds a tab index to each element on the
>> page, to make sure that all elements can be tabbed to. If you're interested
>> in that I would be happy to play with the idea and see what I can come up
>> with.
>>
>> Quentin
>>
>> On Tue, Sep 22, 2015 at 4:33 AM, Jeffery Mewtamer <mewtamer@gmail.[redacted]>
>> wrote:
>>
>>> Sorry for not thinking to include an example of a page showing the
>>> problem.
>>>
>>> Here's the page that pushed me from finding it an easily ignored
>>> inconvenience to wanting to find a solution:
>>> https://www.zintellect.com/Account/Register
>>>
>>> On the linked page, the offending element is the register link(tabbing
>>> jumps straight from cancel to help).
>>>
>>> Okay, just thought to do an experiment: I don't know if the function
>>> is part of Iceweasel/Firefox or an accessibility feature added by
>>> Orca, but pressing various buttons on my keyboard will cause my cursor
>>> to jump between page elements of a given type. Normally, I just use
>>> h(for headings at all levels) 1-6(for headings at specific levels) and
>>> t(for tables) for quickly navigating pages, but it turns out that
>>> there is such a shortcut for clickables(the a key). This should mean I
>>> now have a way of putting focus on a clickable and just need a way to
>>> activate them without a mouse(though clicking my laptop's touchpad
>>> might work if I reinstall xserver-input-mouse, but then I have to
>>> worry about the noise generated when accidental contact is made with
>>> the touchpad).
>>>
>>> On 9/22/15, Quentin Young <qlyoung@ncsu.[redacted]> wrote:
>>> > Hi Jeffery,
>>> >
>>> > Can you possibly link me to a webpage exhibiting this behavior? I
>>> haven't
>>> > found anything existing that fits your needs but I have an idea for an
>>> easy
>>> > implementation.
>>> >
>>> > Quentin
>>> >
>>> > On Mon, Sep 21, 2015 at 6:37 AM, Jeffery Mewtamer <mewtamer@gmail.[redacted]>
>>> > wrote:
>>> >
>>> >> Good morning,
>>> >>
>>> >> I use Iceweasel/Firefox in combination with the Orca screenreader for
>>> >> browsing the Internet, and there's one bit of bad web design that
>>> >> keeps rearing its ugly head: Buttons and other web controls that orca
>>> >> identifies as being clickable. I can't use a mouse, they get skipped
>>> >> over when tabbing between links and form elements, and the enter and
>>> >> space keys do nothing if I manually position the cursor on them.
>>> >> Google would indicate that this is a fairly well known problem in the
>>> >> area of web accessibility, but every fix I've found via Google has
>>> >> been targeted at web designers who want the greater visual flexibility
>>> >> such elements allow without rendering their pages unusable to screen
>>> >> reader users. I've been unable to find anything that assists with
>>> >> making these elements accessible on the end-user side of things.
>>> >>
>>> >> Anyone have any suggestions for possible solutions?incerely,
>>> >>
>>> >> Jeffery Wright
>>> >> President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
>>> >> Former Secretary, Student Government Association, College of the
>>> >> Albemarle.
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Quentin Young
>>> > Vice President, LUG @ NC State
>>> >
>>>
>>>
>>> --
>>> Sincerely,
>>>
>>> Jeffery Wright
>>> President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
>>> Former Secretary, Student Government Association, College of the
>>> Albemarle.
>>>
>>
>>
>>
>> --
>> Quentin Young
>> Vice President, LUG @ NC State
>>
>
>
[Attachment of type text/html removed.]
------------------------------
End of [lug] Digest (5 messages)
**********